Adding fine-grained VAD params to Sarvam saaras:v3 STT plugin#5563
Merged
tinalenguyen merged 1 commit intoMay 12, 2026
Merged
Conversation
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
Contributor
Author
|
@tinalenguyen requesting your review here |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The Sarvam STT WebSocket endpoint for saaras:v3 now accepts granular
VAD tuning parameters. Add support for: positive_speech_threshold,
negative_speech_threshold, min_speech_frames, first_turn_min_speech_frames,
negative_frames_count, negative_frames_window, start_speech_volume_threshold,
interrupt_min_speech_frames, pre_speech_pad_frames, and
num_initial_ignored_frames.
These are gated behind a new
supports_vad_paramsflag in ModelConfig,set to true only for saaras:v3. Parameters flow through STT.init,
stream(), and into the WebSocket query string via _build_websocket_url.
All are optional and only sent when explicitly provided.